You don't really need to mess with SocketFactory, you can use
POE::Component::Client::TCP and write a filter for it to use, which is
pretty easy. Then the ServerInput event would be called for every full
message you receive in a data structure thats easy to use.
David
---------- Original Message -----------
From: "Jay Strauss" <[EMAIL PROTECTED]>
To: "David Davis" <[EMAIL PROTECTED]>
Sent: Tue, 10 Feb 2004 20:40:12 -0600
Subject: Re: Using POE::Wheel::SocketFactory
> There isn't one, I had to dissect the vendor supplied java client to
> determine the messages. The way the conversation goes is:
>
> poe> connected to socket
> server>responds, sending it's version
> poe> sends a clientid
>
> Then in a infinite loop
>
> server>sends (messageID, messageVersion, (list of data values))
> poe>reads (messageID, messageVersion), dispatch proper routine based
> on messageID, proper routine> read data values based on the messageVersion;
>
> end loop
>
> Does this help?
> Jay
> ----- Original Message -----
> From: "David Davis" <[EMAIL PROTECTED]>
> To: "Jay Strauss" <[EMAIL PROTECTED]>
> Sent: Tuesday, February 10, 2004 5:54 PM
> Subject: Re: Using POE::Wheel::SocketFactory
>
> > where's the spec for this protocol?
> >
> > ---------- Original Message -----------
> > From: "Jay Strauss" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Tue, 10 Feb 2004 09:13:18 -0600
> > Subject: Re: Using POE::Wheel::SocketFactory
> >
> > > Hi,
> > >
> > > I get what you say, with
> > >
> > > > You could build a list
> > > > of fields until @record == $record_length{$record[0]} or something.
> At
> > > > that point, you call whatever you've written to handle the record.
> > >
> > > I'm working on getting something to process the list in a timely
> > > fashion, but only once all the elements are there.
> > >
> > > Thanks
> > > Jay
> > ------- End of Original Message -------
> >
> >
> >
------- End of Original Message -------
