I do not know PHP, consider to write a CGI with this technology and
have the following question.
Is it possible to invoke a PHP script and let it endlessly wait for
requests from a website (a Java applet in my case) and serve the
requests when they arrive? I want to avoid loading the script for each
request.
In other words, can it function, in this sense, like a Java servlet?
14  2014 
On Jun 1, 3:00 am, DavidNorep <avdavid.nore...@gmail.comwrote:
I do not know PHP, consider to write a CGI with this technology and
have the following question.
Is it possible to invoke a PHP script and let it endlessly wait for
requests from a website (a Java applet in my case) and serve the
requests when they arrive? I want to avoid loading the script for each
request.
In other words, can it function, in this sense, like a Java servlet?
What is the specific reason that you want to avoid loading the script
for each request?
To save time, to be able to respond to more requests.
I have also another question which is probably general for every CGI,
no matter in which technology it is implemented.
Suppose that a CGI is running and another request arrives, i.e., it is
invoked by another visitor to the website; will another instance of
the CGI start running or will the second request wait until the
running CGI finishes its work or is there a way to control this
behaviour.
"DavidNorep" <av*************@gmail.comwrote in message
news:11**********************@q75g2000hsh.googlegr oups.com...
To save time, to be able to respond to more requests.
I have also another question which is probably general for every CGI,
no matter in which technology it is implemented.
Suppose that a CGI is running and another request arrives, i.e., it is
invoked by another visitor to the website; will another instance of
the CGI start running or will the second request wait until the
running CGI finishes its work or is there a way to control this
behaviour.
I think programs like Apache are used to handling multiple requests at one
time. In a multi-user environment though you need to account for multiple
people making changes at the same time and the potential conflict with
people changing the same thing at the same time.
Tom
--
Newsguy.com - Unlimited Accounts
Now with 32 concurrent connections
On Jun 1, 2:01 pm, DavidNorep <avdavid.nore...@gmail.comwrote:
To save time, to be able to respond to more requests.
I have also another question which is probably general for every CGI,
no matter in which technology it is implemented.
Suppose that a CGI is running and another request arrives, i.e., it is
invoked by another visitor to the website; will another instance of
the CGI start running or will the second request wait until the
running CGI finishes its work or is there a way to control this
behaviour.
Read this article, particularly Tip #5:
< http://www.ibm.com/developerworks/li...-code/?ca=dgr-
FClnxw01linuxcodetips>
On Jun 1, 12:00 am, DavidNorep <avdavid.nore...@gmail.comwrote:
>
I do not know PHP, consider to write a CGI with this technology and
have the following question.
Is it possible to invoke a PHP script and let it endlessly wait for
requests from a website (a Java applet in my case) and serve the
requests when they arrive? I want to avoid loading the script for
each request.
No. But you don't have to configure your PHP setup as CGI;
configuring
it as an Apache module with an accelerator will do pretty much what
you
want; at the first call, the script will be compiled into bytecode
and
the bytecode will be cached, so beginning with the second call, the
script will not be loaded; cached bytecode will be used instead.
In other words, can it function, in this sense, like a Java servlet?
PHP is not Java. If you want something to function like a Java
servlet,
you should implement it as a Java servlet.
Cheers,
NC
On Jun 1, 11:01 am, DavidNorep <avdavid.nore...@gmail.comwrote:
>
I have also another question which is probably general for every
CGI, no matter in which technology it is implemented.
Nope; it's highly specific to the OS and HTTP server.
Suppose that a CGI is running and another request arrives, i.e.,
it is invoked by another visitor to the website; will another
instance of the CGI start running or will the second request wait
until the running CGI finishes its work
If the second request arrives and the HTTP server has enough
resources remaining to serve a response, it will. If the second
request arrives and the HTTP server does not have enough resources
remaining to serve a response, the second client will wait as
long as it is configured to do, then time out.
is there a way to control this behaviour.
Yes, but you have to code for it. Every instance of the script
must start by checking if it is the only one running (there are
many ways to get this done). If it is, it should keep running;
if it isn't, it should issue a "Location:" header to redirect
the client to itself.
Cheers,
NC
DavidNorep wrote:
I do not know PHP, consider to write a CGI with this technology and
have the following question.
Is it possible to invoke a PHP script and let it endlessly wait for
requests from a website (a Java applet in my case) and serve the
requests when they arrive? I want to avoid loading the script for each
request.
Yes, but only for output. I done web chat with this technology (I
call it endless connection) long time ago, before AJAX era. It was PHP
script on server-side and javascript on client-side. You need
set_time_limit() to prevent timeout on server so you can't do it in safe
mode. And you need to send periodically something to prevent timeout on
client. Request sent to additional short script who put it to database
or another place. Main script in endless loop checks for new requests,
process it and sends result back to client.
Now here is no reasons to do such things.
"Alexey Kulentsov" <cr*******@crimaniak.comschreef in bericht
news:46***********************@news.sunsite.dk...
DavidNorep wrote:
>I do not know PHP, consider to write a CGI with this technology and
have the following question.
Is it possible to invoke a PHP script and let it endlessly wait for
requests from a website (a Java applet in my case) and serve the
requests when they arrive? I want to avoid loading the script for each
request.
Yes, but only for output. I done web chat with this technology (I call
it endless connection) long time ago, before AJAX era. It was PHP script
on server-side and javascript on client-side. You need set_time_limit() to
prevent timeout on server so you can't do it in safe mode. And you need to
send periodically something to prevent timeout on client. Request sent to
additional short script who put it to database or another place. Main
script in endless loop checks for new requests, process it and sends
result back to client.
Now here is no reasons to do such things.
Correct me if I'm wrong here, but I thought there was some sort of solution
for this, using sockets. Or is this perhaps what you are refering to
already?
I once ran a very small test with socket connections as a command line
script. My goal was to write a little http chat app. I didn't follow up on
that anymore. But I had the feeling though that this little script could
easily be ported to some webserver environment. Probably not too a stressful
environment, but still.
@ DavidNorep: you mentioned the use of a JAVA applet. I don't know much
about JAVA but I assume JAVA has some socket interfaces itself too, no? This
could rule out client timeouts I think.
Also, I vaguely recall the script didn't need to loop, it would just
listened to a socket, and started doing things as soon as it got input on
the socket. I'll have look around to see if I can find the script.
In the meanwhile do a search for sockets. That should give you some
direction.
"amygdala" <no*****@noreply.comschreef in bericht
news:46***********************@news.kpnplanet.nl.. .
>
"Alexey Kulentsov" <cr*******@crimaniak.comschreef in bericht
news:46***********************@news.sunsite.dk...
>DavidNorep wrote:
>>I do not know PHP, consider to write a CGI with this technology and
have the following question.
Is it possible to invoke a PHP script and let it endlessly wait for
requests from a website (a Java applet in my case) and serve the
requests when they arrive? I want to avoid loading the script for each
request.
Yes, but only for output. I done web chat with this technology (I call
it endless connection) long time ago, before AJAX era. It was PHP script
on server-side and javascript on client-side. You need set_time_limit()
to prevent timeout on server so you can't do it in safe mode. And you
need to send periodically something to prevent timeout on client. Request
sent to additional short script who put it to database or another place.
Main script in endless loop checks for new requests, process it and sends
result back to client.
Now here is no reasons to do such things.
Correct me if I'm wrong here, but I thought there was some sort of
solution for this, using sockets. Or is this perhaps what you are refering
to already?
I once ran a very small test with socket connections as a command line
script. My goal was to write a little http chat app. I didn't follow up on
that anymore. But I had the feeling though that this little script could
easily be ported to some webserver environment. Probably not too a
stressful environment, but still.
@ DavidNorep: you mentioned the use of a JAVA applet. I don't know much
about JAVA but I assume JAVA has some socket interfaces itself too, no?
This could rule out client timeouts I think.
Also, I vaguely recall the script didn't need to loop, it would just
listened to a socket, and started doing things as soon as it got input on
the socket. I'll have look around to see if I can find the script.
Forget what I said about not having to loop. It *did* need to loop. I found
the core of the script I used in the PHP manual under Socket Functions. I
remember again.
HTH
amygdala wrote:
"Alexey Kulentsov" <cr*******@crimaniak.comschreef in bericht
news:46***********************@news.sunsite.dk...
>DavidNorep wrote:
>>I do not know PHP, consider to write a CGI with this technology and
have the following question.
Is it possible to invoke a PHP script and let it endlessly wait for
requests from a website (a Java applet in my case) and serve the
requests when they arrive? I want to avoid loading the script for each
request.
Yes, but only for output. I done web chat with this technology (I call
it endless connection) long time ago, before AJAX era. It was PHP script
on server-side and javascript on client-side. You need set_time_limit() to
prevent timeout on server so you can't do it in safe mode. And you need to
send periodically something to prevent timeout on client. Request sent to
additional short script who put it to database or another place. Main
script in endless loop checks for new requests, process it and sends
result back to client.
Now here is no reasons to do such things.
Correct me if I'm wrong here, but I thought there was some sort of solution
for this, using sockets. Or is this perhaps what you are refering to
already?
I once ran a very small test with socket connections as a command line
script. My goal was to write a little http chat app. I didn't follow up on
that anymore. But I had the feeling though that this little script could
easily be ported to some webserver environment. Probably not too a stressful
environment, but still.
Good thing you didn't follow up with this though. A socket-attached
script is much different than a web-based one.
@ DavidNorep: you mentioned the use of a JAVA applet. I don't know much
about JAVA but I assume JAVA has some socket interfaces itself too, no? This
could rule out client timeouts I think.
Yes, java has socket interfaces. But it doesn't rule out client timeouts.
Also, I vaguely recall the script didn't need to loop, it would just
listened to a socket, and started doing things as soon as it got input on
the socket. I'll have look around to see if I can find the script.
In the meanwhile do a search for sockets. That should give you some
direction.
As I said - socket interfaces are much different that web-based ones.
For one thing - sockets typically stay open as long as the chat (or
whatever) session is active. Sockets used for HTTP are closed at the
end of each page.
A BIG difference.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp. js*******@attglobal.net
==================
"Jerry Stuckle" <js*******@attglobal.netschreef in bericht
news:Yr******************************@comcast.com. ..
amygdala wrote:
>"Alexey Kulentsov" <cr*******@crimaniak.comschreef in bericht
news:46***********************@news.sunsite.dk. ..
>>DavidNorep wrote:
I do not know PHP, consider to write a CGI with this technology and
have the following question.
Is it possible to invoke a PHP script and let it endlessly wait for
requests from a website (a Java applet in my case) and serve the
requests when they arrive? I want to avoid loading the script for each
request.
Yes, but only for output. I done web chat with this technology (I call
it endless connection) long time ago, before AJAX era. It was PHP script
on server-side and javascript on client-side. You need set_time_limit()
to prevent timeout on server so you can't do it in safe mode. And you
need to send periodically something to prevent timeout on client.
Request sent to additional short script who put it to database or
another place. Main script in endless loop checks for new requests,
process it and sends result back to client.
Now here is no reasons to do such things.
Correct me if I'm wrong here, but I thought there was some sort of
solution for this, using sockets. Or is this perhaps what you are
refering to already?
I once ran a very small test with socket connections as a command line
script. My goal was to write a little http chat app. I didn't follow up
on that anymore. But I had the feeling though that this little script
could easily be ported to some webserver environment. Probably not too a
stressful environment, but still.
Good thing you didn't follow up with this though. A socket-attached
script is much different than a web-based one.
>@ DavidNorep: you mentioned the use of a JAVA applet. I don't know much
about JAVA but I assume JAVA has some socket interfaces itself too, no?
This could rule out client timeouts I think.
Yes, java has socket interfaces. But it doesn't rule out client timeouts.
>Also, I vaguely recall the script didn't need to loop, it would just
listened to a socket, and started doing things as soon as it got input on
the socket. I'll have look around to see if I can find the script.
In the meanwhile do a search for sockets. That should give you some
direction.
As I said - socket interfaces are much different that web-based ones. For
one thing - sockets typically stay open as long as the chat (or whatever)
session is active. Sockets used for HTTP are closed at the end of each
page.
A BIG difference.
Hmm, I probably didn't express myself good enough then. Or perhaps I'm
missing essential knowledge here. But the point I was hoping to get accross
was, that perhaps because JAVA can handle socket connections it wouldn't
have to be an HTTP socket that the applet connects to. Rather it could
maintain a statefull connection on some port? Does that make any sense? Or
am I talking complete rubbish here? Could very well be. ;-) Cause my
networking knowledge is very poor.
amygdala wrote:
"Jerry Stuckle" <js*******@attglobal.netschreef in bericht
news:Yr******************************@comcast.com. ..
>amygdala wrote:
>>"Alexey Kulentsov" <cr*******@crimaniak.comschreef in bericht
news:46***********************@news.sunsite.dk.. .
DavidNorep wrote:
I do not know PHP, consider to write a CGI with this technology and
have the following question.
>
Is it possible to invoke a PHP script and let it endlessly wait for
requests from a website (a Java applet in my case) and serve the
requests when they arrive? I want to avoid loading the script for each
request.
Yes, but only for output. I done web chat with this technology (I call
it endless connection) long time ago, before AJAX era. It was PHP script
on server-side and javascript on client-side. You need set_time_limit()
to prevent timeout on server so you can't do it in safe mode. And you
need to send periodically something to prevent timeout on client.
Request sent to additional short script who put it to database or
another place. Main script in endless loop checks for new requests,
process it and sends result back to client.
Now here is no reasons to do such things.
Correct me if I'm wrong here, but I thought there was some sort of
solution for this, using sockets. Or is this perhaps what you are
refering to already?
I once ran a very small test with socket connections as a command line
script. My goal was to write a little http chat app. I didn't follow up
on that anymore. But I had the feeling though that this little script
could easily be ported to some webserver environment. Probably not too a
stressful environment, but still.
Good thing you didn't follow up with this though. A socket-attached
script is much different than a web-based one.
>>@ DavidNorep: you mentioned the use of a JAVA applet. I don't know much
about JAVA but I assume JAVA has some socket interfaces itself too, no?
This could rule out client timeouts I think.
Yes, java has socket interfaces. But it doesn't rule out client timeouts.
>>Also, I vaguely recall the script didn't need to loop, it would just
listened to a socket, and started doing things as soon as it got input on
the socket. I'll have look around to see if I can find the script.
In the meanwhile do a search for sockets. That should give you some
direction.
As I said - socket interfaces are much different that web-based ones. For
one thing - sockets typically stay open as long as the chat (or whatever)
session is active. Sockets used for HTTP are closed at the end of each
page.
A BIG difference.
Hmm, I probably didn't express myself good enough then. Or perhaps I'm
missing essential knowledge here. But the point I was hoping to get accross
was, that perhaps because JAVA can handle socket connections it wouldn't
have to be an HTTP socket that the applet connects to. Rather it could
maintain a statefull connection on some port? Does that make any sense? Or
am I talking complete rubbish here? Could very well be. ;-) Cause my
networking knowledge is very poor.
You made a comment: "My goal was to write a little http chat app."
Is this an http app? If so, the client will get timeouts - it can't be
helped. It's part of the protocol (and built into the browsers), no
matter what port you're running on (and no, http is not restricted to
port 80, although that's the most common one). But in general you'll
want some kind of webserver to help with the connections and processing.
If it's not a http app, you have more control over timeouts, although
they can still occur. But you won't be able to use browsers.
You can set up connections on many ports. But there's a lot more to
handling network connections than just opening a port - especially if
you're going to have multiple people connecting. And that's true in any
language.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp. js*******@attglobal.net
==================
"Jerry Stuckle" <js*******@attglobal.netschreef in bericht
news:Zb******************************@comcast.com. ..
amygdala wrote:
>"Jerry Stuckle" <js*******@attglobal.netschreef in bericht
news:Yr******************************@comcast.com ...
>>amygdala wrote:
"Alexey Kulentsov" <cr*******@crimaniak.comschreef in bericht
news:46***********************@news.sunsite.dk. ..
DavidNorep wrote:
>I do not know PHP, consider to write a CGI with this technology and
>have the following question.
>>
>Is it possible to invoke a PHP script and let it endlessly wait for
>requests from a website (a Java applet in my case) and serve the
>requests when they arrive? I want to avoid loading the script for
>each
>request.
Yes, but only for output. I done web chat with this technology (I
call it endless connection) long time ago, before AJAX era. It was PHP
script on server-side and javascript on client-side. You need
set_time_limit() to prevent timeout on server so you can't do it in
safe mode. And you need to send periodically something to prevent
timeout on client. Request sent to additional short script who put it
to database or another place. Main script in endless loop checks for
new requests, process it and sends result back to client.
Now here is no reasons to do such things.
Correct me if I'm wrong here, but I thought there was some sort of
solution for this, using sockets. Or is this perhaps what you are
refering to already?
I once ran a very small test with socket connections as a command line
script. My goal was to write a little http chat app. I didn't follow up
on that anymore. But I had the feeling though that this little script
could easily be ported to some webserver environment. Probably not too
a stressful environment, but still.
Good thing you didn't follow up with this though. A socket-attached
script is much different than a web-based one.
@ DavidNorep: you mentioned the use of a JAVA applet. I don't know
much about JAVA but I assume JAVA has some socket interfaces itself
too, no? This could rule out client timeouts I think.
Yes, java has socket interfaces. But it doesn't rule out client
timeouts.
Also, I vaguely recall the script didn't need to loop, it would just
listened to a socket, and started doing things as soon as it got input
on the socket. I'll have look around to see if I can find the script.
In the meanwhile do a search for sockets. That should give you some
direction.
As I said - socket interfaces are much different that web-based ones.
For one thing - sockets typically stay open as long as the chat (or
whatever) session is active. Sockets used for HTTP are closed at the
end of each page.
A BIG difference.
Hmm, I probably didn't express myself good enough then. Or perhaps I'm
missing essential knowledge here. But the point I was hoping to get
accross was, that perhaps because JAVA can handle socket connections it
wouldn't have to be an HTTP socket that the applet connects to. Rather it
could maintain a statefull connection on some port? Does that make any
sense? Or am I talking complete rubbish here? Could very well be. ;-)
Cause my networking knowledge is very poor.
You made a comment: "My goal was to write a little http chat app."
Yes you are right, my bad, slip of the tongue. I was implying a chat app
which would be build in a website (hence the 'incorrect' http comment). I
understand this is not correct terminology. I on occasion mix up
terminology. I tend to think people see through that and get the big picture
I'm getting after. But I need to watch my terminology better I guess. Mea
culpa ;-)
Is this an http app? If so, the client will get timeouts - it can't be
helped. It's part of the protocol (and built into the browsers), no
matter what port you're running on (and no, http is not restricted to port
80, although that's the most common one). But in general you'll want some
kind of webserver to help with the connections and processing.
If it's not a http app, you have more control over timeouts, although they
can still occur. But you won't be able to use browsers.
You can set up connections on many ports. But there's a lot more to
handling network connections than just opening a port - especially if
you're going to have multiple people connecting. And that's true in any
language.
I can easily imagine this to be true Jerry, but then, that's not what the OP
asked. The OP asked whether it was possible.
amygdala wrote:
"Jerry Stuckle" <js*******@attglobal.netschreef in bericht
news:Zb******************************@comcast.com. ..
>amygdala wrote:
>>"Jerry Stuckle" <js*******@attglobal.netschreef in bericht
news:Yr******************************@comcast.co m...
amygdala wrote:
"Alexey Kulentsov" <cr*******@crimaniak.comschreef in bericht
news:46***********************@news.sunsite.dk ...
>DavidNorep wrote:
>>I do not know PHP, consider to write a CGI with this technology and
>>have the following question.
>>>
>>Is it possible to invoke a PHP script and let it endlessly wait for
>>requests from a website (a Java applet in my case) and serve the
>>requests when they arrive? I want to avoid loading the script for
>>each
>>request.
> Yes, but only for output. I done web chat with this technology (I
>call it endless connection) long time ago, before AJAX era. It was PHP
>script on server-side and javascript on client-side. You need
>set_time_limit() to prevent timeout on server so you can't do it in
>safe mode. And you need to send periodically something to prevent
>timeout on client. Request sent to additional short script who put it
>to database or another place. Main script in endless loop checks for
>new requests, process it and sends result back to client.
> Now here is no reasons to do such things.
Correct me if I'm wrong here, but I thought there was some sort of
solution for this, using sockets. Or is this perhaps what you are
refering to already?
>
I once ran a very small test with socket connections as a command line
script. My goal was to write a little http chat app. I didn't follow up
on that anymore. But I had the feeling though that this little script
could easily be ported to some webserver environment. Probably not too
a stressful environment, but still.
>
Good thing you didn't follow up with this though. A socket-attached
script is much different than a web-based one.
@ DavidNorep: you mentioned the use of a JAVA applet. I don't know
much about JAVA but I assume JAVA has some socket interfaces itself
too, no? This could rule out client timeouts I think.
>
Yes, java has socket interfaces. But it doesn't rule out client
timeouts.
Also, I vaguely recall the script didn't need to loop, it would just
listened to a socket, and started doing things as soon as it got input
on the socket. I'll have look around to see if I can find the script.
>
In the meanwhile do a search for sockets. That should give you some
direction.
As I said - socket interfaces are much different that web-based ones.
For one thing - sockets typically stay open as long as the chat (or
whatever) session is active. Sockets used for HTTP are closed at the
end of each page.
A BIG difference.
Hmm, I probably didn't express myself good enough then. Or perhaps I'm
missing essential knowledge here. But the point I was hoping to get
accross was, that perhaps because JAVA can handle socket connections it
wouldn't have to be an HTTP socket that the applet connects to. Rather it
could maintain a statefull connection on some port? Does that make any
sense? Or am I talking complete rubbish here? Could very well be. ;-)
Cause my networking knowledge is very poor.
You made a comment: "My goal was to write a little http chat app."
Yes you are right, my bad, slip of the tongue. I was implying a chat app
which would be build in a website (hence the 'incorrect' http comment). I
understand this is not correct terminology. I on occasion mix up
terminology. I tend to think people see through that and get the big picture
I'm getting after. But I need to watch my terminology better I guess. Mea
culpa ;-)
>Is this an http app? If so, the client will get timeouts - it can't be
helped. It's part of the protocol (and built into the browsers), no
matter what port you're running on (and no, http is not restricted to port
80, although that's the most common one). But in general you'll want some
kind of webserver to help with the connections and processing.
If it's not a http app, you have more control over timeouts, although they
can still occur. But you won't be able to use browsers.
You can set up connections on many ports. But there's a lot more to
handling network connections than just opening a port - especially if
you're going to have multiple people connecting. And that's true in any
language.
I can easily imagine this to be true Jerry, but then, that's not what the OP
asked. The OP asked whether it was possible.
Yes, and there's a big difference between *possible* and *practical*.
It's possible for me to build a 747. All the technical details are
easily available. But it's not practical.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp. js*******@attglobal.net
================== This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: comp.lang.php |
last post by:
I've heard numerous and varied commentaries here and on other fora
regarding PHP and the concept of threads. Coming from a Java
background I understand how threads benefit to prevent collisions,...
|
by: Jim |
last post by:
Hi,
I keep getting form results emailed to me that would indicate a form
from my web site is getting submitted with all fields blank or empty,
but my code should preventing users from proceeding...
|
by: S P Arif Sahari Wibowo |
last post by:
Hi!
I am thinking to have a client-side script doing processing on file
downloading, basically the script will process a downloaded file from the
server before it received by the user. For...
|
by: Adrian MacNair |
last post by:
Hi,
I created an image gallery which displays 63 images in a slideshow. The
problem is that the show was slow because each image loaded one at a time
during the show. No problem right? I just...
|
by: John Richardson |
last post by:
I've been bothered for some time about my DataGrid not populating my rows
very quickly. I have about 10K rows loading into the grid.
I create a datatable dt with 2 columns, an ID and a display. ...
|
by: Daniel |
last post by:
Hi,
Does anyone know if it is possible to put an aspx page inside of another? OR
run an aspx page and capture the output as a string and then write this out
to a page....
So for example say...
|
by: Venkatesh |
last post by:
Hello All,
I have couple of doubts regarding the concept of on-demand javascript
loading using javascript code. I could see on the net different
techniques for achieving this - techniques like:...
|
by: VeeraLakshmi |
last post by:
I am doing a project for internet control using Java,PHP and MySql.All sites
should go through the proxy server only.We are giving access rights as allow or
deny to the sites.If we type the...
|
by: dtown22 |
last post by:
I am trying to make a copy of all the files involved in a web request
from a specific website (i.e. you enter groups.google.com, and hit
enter once and then basically make a copy of all the files...
|
by: CloudSolutions |
last post by:
Introduction:
For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
|
by: Faith0G |
last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...
|
by: ryjfgjl |
last post by:
In our work, we often need to import Excel data into databases (such as MySQL, SQL Server, Oracle) for data analysis and processing. Usually, we use database tools like Navicat or the Excel import...
|
by: taylorcarr |
last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
| |
